[Instances] Cancel a compute instance at the end of its billing period
Requests cancellation at the end of the current billing period, exactly as cancel_instance does: nothing is deleted now. The instance keeps running and billing until billing_end_date, and revoke_instance_cancellation (POST revoke-cancellation) withdraws the request until then. An optional JSON body takes the fields of cancel_instance: reason_code, among too_expensive, no_longer_needed, missing_feature, technical_issue, switching_provider, other, defaulting to no_longer_needed; and reason, a sentence of at least seven words, defaulting to a fixed one. Idempotent: an instance whose cancellation is already requested, or that is already terminated or cancelled, answers 202 with its current state and nothing is requested again.
Authorizations
Path Parameters
Response
Cancellation requested, or already requested or effective; the instance in its state
free- Freeone_time- One Timehourly- Hourlymonthly- Monthlyquarterly- Quarterlysemi_annually- Semi-Annuallyannually- Annuallybiennially- Bienniallytriennially- Triennially
free, one_time, hourly, monthly, quarterly, semi_annually, annually, biennially, triennially Reason picked for cancellation
too_expensive- Too expensiveno_longer_needed- No longer neededmissing_feature- Missing featuretechnical_issue- Technical issueswitching_provider- Moving to another providerother- Other
too_expensive, no_longer_needed, missing_feature, technical_issue, switching_provider, other 
